Reduce usage of Ant #10059

basil · 2024-12-13T22:49:09Z

While reading this code recently, I noticed we were using Ant for functionality that is now present in the Java Platform. Easier to maintain code that has fewer third-party library dependencies.

Testing done

mvn clean verify -Dtest=hudson.model.DirectoryBrowserSupportTest,jenkins.util.VirtualFileTest

Proposed changelog entries

N/A

Proposed upgrade guidelines

N/A

Submitter checklist

Give feedback

The Jira issue, if it exists, is well-described.
The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
There is automated testing or an explanation as to why this change has no tests.
New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
For dependency updates, there are links to external changelogs and, if possible, full differentials.
For new APIs and extension points, there is a link to at least one consumer.
Options

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Give feedback

There are at least two (2) approvals for the pull request and no outstanding requests for change.
Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
Proper changelog labels are set so that the changelog can be generated automatically.
If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
Options

MarkEWaite · 2024-12-14T14:48:21Z

/
This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback.

/label ready-for-merge

Reduce usage of Ant

9361455

basil added the skip-changelog Should not be shown in the changelog label Dec 13, 2024

MarkEWaite approved these changes Dec 13, 2024

View reviewed changes

NotMyFault approved these changes Dec 14, 2024

View reviewed changes

comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Dec 14, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Reduce usage of Ant #10059

Reduce usage of Ant #10059

basil commented Dec 13, 2024

Submitter checklist

Maintainer checklist

MarkEWaite commented Dec 14, 2024

Reduce usage of Ant #10059

Are you sure you want to change the base?

Reduce usage of Ant #10059

Conversation

basil commented Dec 13, 2024

Testing done

Proposed changelog entries

Proposed upgrade guidelines

Submitter checklist

Desired reviewers

Maintainer checklist

MarkEWaite commented Dec 14, 2024